Skip to content

Improve displayed error by using DataFusionError's Display trait#1370

Merged
timsaucer merged 2 commits intoapache:mainfrom
rerun-io:antoine/better-dfn-error
Feb 4, 2026
Merged

Improve displayed error by using DataFusionError's Display trait#1370
timsaucer merged 2 commits intoapache:mainfrom
rerun-io:antoine/better-dfn-error

Conversation

@abey79
Copy link
Contributor

@abey79 abey79 commented Feb 4, 2026

Which issue does this PR close?

Closes #1369

Rationale for this change

The error displayed by the snippet in #1369 now is:

Exception: DataFusion error: Schema error: No field named does_not_exist. Valid fields are users.id, users.name, users.age.

It previously was:

Exception: DataFusion error: SchemaError(FieldNotFound { field: Column { relation: None, name: "does_not_exist" }, valid_fields: [Column { relation: Some(Bare { table: "users" }), name: "id" }, Column { relation: Some(Bare { table: "users" }), name: "name" }, Column { relation: Some(Bare { table: "users" }), name: "age" }] }, Some(""))

What changes are included in this PR?

This uses the Display trait instead of the Debug trait of DataFusionError when displaying errors.

Are there any user-facing changes?

Yes. Error display.

@abey79 abey79 mentioned this pull request Feb 4, 2026
Open
@abey79 abey79 force-pushed the antoine/better-dfn-error branch from 367dce9 to 97f5f46 Compare February 4, 2026 15:37
@timsaucer timsaucer merged commit adec2dc into apache:main Feb 4, 2026
17 checks passed
@abey79 abey79 deleted the antoine/better-dfn-error branch February 5, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@timsaucer timsaucer timsaucer approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Improve display of schema error

2 participants

@abey79 @timsaucer